feat(button)!: port to <pf-v6-button> - #3157
Conversation
🦋 Changeset detectedLatest commit: 72754ed The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Commitlint tests passed!More Info{
"valid": true,
"errors": [],
"warnings": [],
"input": "feat(button)!: port to `<pf-v6-button>`"
} |
Prevent Chromium Tab-wrap flakiness with a trailing focus sentinel, stop RovingTabindexController from stealing focus after Tab-out, pin timestamp fixtures to en-US, and add the missing major changeset for the v5→v6 button port. Assisted-By: Cursor Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Deploy Preview for patternfly-elements ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
<pf-v6-button>
…check Co-authored-by: Cursor <cursoragent@cursor.com> # Conflicts: # elements/pf-v5-clipboard-copy/pf-v5-clipboard-copy.ts # elements/pf-v5-tooltip/demo/block-triggers.html # elements/pf-v5-tooltip/demo/flip.html # elements/pf-v5-tooltip/demo/performance.html # elements/pf-v5-tooltip/demo/trigger.html # elements/pf-v5-tooltip/docs/pf-v5-tooltip.md
This comment has been minimized.
This comment has been minimized.
|
@ArathyKumar, Since we don't hvae Qodo enabled for this repo: have you had an agent review this PR yet? I had Grok review it in the Qodo style. This feedback will need to be vetted. Results below: AI review resultsCode Review 🐞 Bugs (3) 1.
|
What I did
Ported the existing pf-v5-button Web Component to a new pf-v6-button Web Component that follows design and provides feature parity with the PatternFly v6 Button React component.
Changes
Testing Instructions
Notes to Reviewers
This PR ports the existing pf-v5-button Web Component to pf-v6-button and brings it in line with the PatternFly v6 React Button.
For more details about the requirements and expected behavior, please refer to the related issue #2984.